Electronic financial management and analysis system and related methods

ABSTRACT

A computing system facilitating electronic bill presentment and payment features for authorized users via a user interface is introduced including an analysis engine. The analysis engine, in response to user interaction with the user interface, selectively performs user-defined analysis on at least a subset of retrieved billing information associated with one or more billers. The analysis engine further generates one or more user-defined report(s) based, at least in part, on the user-defined analysis.

TECHNICAL FIELD

This invention generally relates to data analysis systems and, more particularly, to an electronic financial management and analysis system and related methods.

BACKGROUND

Electronic bill presentment and payment (EBPP) systems are known. Indeed, a number of businesses provide their customers with the opportunity to access billing information electronically review the bill and electronically settle account debts. As an extension of this service, a number of companies such as, for example, CheckFree Corporation of Atlanta, Ga., accept billing information from a number of businesses for presentment and payment by subscribing consumers. In addition to the inherent convenience of reviewing and paying bills electronically, such services have an added feature of consolidating bills from a number of different creditors (billers) for review and payment from a single location (e.g., a single web-site). The acceptance of such systems has grown at a healthy rate over the last couple of years, as more and more consumers become comfortable with the idea of executing financial transactions over a public data network (i.e., the Internet).

While the EBPP systems have been gaining in popularity with individual consumers, its use by business (or corporate) customer's for billing other businesses (or corporate) customer's has not grown at the same rate. One reason that corporate customers have been slow to utilize the EBPP services of their purveyors is their need to analyze and track billing information. Take telephone bills, for example. Many telephone companies provide their customer's with the option of reviewing and paying their telephone bills online using their, or another company's (e.g., CheckFree) EBPP system. It is to be appreciated, however, that a telephone bill for a corporate customer can be infinitely more complex than that of a typical consumer. Unlike the typical consumer telephone bill, a corporate telephone bill will likely contain several different accounts, each containing hundreds or thousands of telephone extensions (numbers), each with hundreds or thousands of records of phone calls per month. Prior art EBPP systems typically loaded billing information in one of two ways. Some EBPP systems scan physical (paper) bills and simply provide authorized users a view of the scanned image. More sophisticated ones of the prior art EBPP systems electronically receive billing information into a flat database for presentation to users in a predefined format, facilitating payment by the authorized users.

In addition to the foregoing technical limitations, presenting such vast amounts of information which, inter alia, may well span several hundred pages (or screens) in an easily navigable form is quite difficult. The user-interfaces of prior art EBPP systems were designed to accommodate a typical consumer's billing information, i.e., which may span several pages but is unlikely to, extend past, say, ten pages. Accordingly, EBPP systems employ a simple paging system with numeric “hyperlinks” to individual pages of the electronic bill. It is to be appreciated that, with hundreds or thousands of pages, such a paging system paradigm begins to fail when applied to corporate customer's. Consequently, many EBPP system providers use a paging system typical of online search engines, wherein the immediate ten (10) pages, requiring a user to hit a “previous” or “next” hyperlink to view the preceding or succeeding ten pages. Again, when a user needs to access page 110 of a 315 page bill, such a paging system is cumbersome at best.

Moreover, a corporate customer often needs access to the data itself for analysis, re-rating (i.e., where an intermediary business marks up billing information on a line-item by line-item basis for presentation to a third-party customer), and control purposes. While certain prior art systems may manually provide users with the data (e.g., on a CD-ROM) for analysis purposes, such “off-line” systems do not support electronic remittance and does not enable the user to manage billing information (e.g., category names, definitions, etc.). Even more limiting than the user interface, though, is the lack of any substantial analysis capability. Prior art EBPP systems do not provide any substantial analysis tools other than, perhaps, different levels of static detail of the billing information. Similarly, the reporting tools are typically limited to 10-60 pre-formatted (or, “canned”) reports. It is easy to understand why such analysis services are not provided. First, providing a user with the requisite access to the billing data necessary to perform such analysis presents a security risk and, as such, an unattractive administrative burden on the EBPP provider. Second, the analysis needs vary from EBPP site to site. Thus, an inordinate amount of costly developer time would have to be spent customizing each customer's site with the desired analysis tools. Moreover, these analysis requirements may very well change over time, further consuming development time.

Those skilled in the art will appreciate that each of the foregoing limitations inherently limit the scalability of such prior art EBPP systems, thereby limiting their ability to accommodate the billing requirements of corporate customers.

Thus, an electronic financial management and analysis system and related methods is required, unencumbered by the inherent limitations commonly associated with prior art EBPP systems. Indeed, what is required is an Electronic Bill Presentment, Analysis and Payment (EBPAP) system. Just such a system is introduced below.

SUMMARY

This invention concerns an electronic financial analysis system and related methods. More specifically, the present invention concerns an electronic bill presentment, analysis and payment (EBPAP) system and related methods is introduced. According to a first example embodiment, a method comprising receiving billing information at a server from one or more billers for presentment to a plurality of users, and selectively invoking a user-defined analysis of at least a subset of the received billing information associated with a user upon receiving an indication to invoke the analysis by the user. In this regard, the EBPAP system extends prior art EBPP systems to accommodate the management and analysis needs of users, corporate and consumer alike.

According to another aspect of the present invention, an automated password reissuance system is presented. According to this aspect of the invention, when a user forgets their password to access and utilize the services of the EBPAP system, the EBPAP system can automatically generate and securely reissue a password to the user, facilitating subsequent access. According to one implementation, a method is presented comprising receiving an indication from a user including information associated with a registered user. Upon identifying the registered user, a password is dynamically generated and assigned to the registered user, whereupon a message is securely communicated to the registered user at a predefined address. The pre-defined address is established upon the original registration of the user and is, therefore, impervious to attacks by imposters posing as a registered user, i.e., the password message would not be sent to the imposter, but to a location securely accessed by the registered user. According to one implementation, the predefined address is one or more of an email account, a facsimile number, a telephone number, a postal address, an account address, a network address, a business address or a home address.

According to another aspect of the present invention, a rate management utility is provided within the EBPAP system. According to this aspect of the present invention, a corporate user can re-rate (e.g., mark-up or down) billing information received from select billers intended for select third parties (e.g., consumers of the corporate user). An example application is where a law firm utilizes the EBPAP system to further mark-up calls made to or received from select clients. Unlike prior art systems which provided for a re-rating at, say, a private branch exchange, the EBPAP system of the present invention enables users to re-rate the billing information directly.

According to another of the present invention, an innovative paging schema is used throughout the EBPAP system to provide users with convenient access to any page within the billing information. According to this aspect, a hierarchical paging system is employed, with a sliding detail window to provide access to any page in the bill with a minimum of interaction with the bill (e.g., mouse-clicks on hyperlinks).

These and other innovative aspects of the present invention will be evident from the detailed description below.

BRIEF DESCRIPTION OF THE DRAWINGS

The same reference numbers are used throughout the figures to reference like components and features.

FIG. 1 is a block diagram of a data network facilitating electronic bill presentment, analysis and payment (EBPAP) services;

FIG. 2 is a block diagram of an example computing system to implement the EBPAP services of the present invention;

FIG. 3 is a block diagram of an example analysis engine to facilitate user-defined analysis of select financial information, according to the teachings of the present invention;

FIG. 4 is a graphical illustration of an example data structure comprising user account information;

FIG. 5 is a graphical representation of an example data structure comprising billing information from one or more billers;

FIG. 6 is a flow chart of an example method for accessing and selectively invoking EBPAP resources, according to one example embodiment;

FIG. 7 is a graphical illustration of an example user interface (UI) facilitating user interaction with the EBPAP system, according to one example implementation;

FIG. 8 is flow chart of an example method for invoking management services of the EBPAP agent;

FIG. 9 is a graphical illustration of an example UI enabling a user to selectively invoke one or more management services, in accordance with one example implementation;

FIG. 10 is a graphical representation of an example UI enabling a user to provide user profile information, according to one implementation of the present invention;

FIGS. 11A-11D provide graphical representations of example UT's enabling a user to customize billing information definitions, dependencies, categories, rate plans, and the like, in accordance with one aspect of the present invention;

FIG. 12 is a flow chart of an example method for the secure, automatic reissuance of a forgotten password, in accordance with one aspect of the present invention;

FIG. 13 is a graphical representation of an example UI facilitating the secure, automatic reissuance of a forgotten password, according to one example implementation;

FIG. 14 is a flow chart of an example method for analysis and report profile management incorporating the teachings of the present invention;

FIG. 15 is a graphical illustration of an example UI facilitating user modification to an existing analysis protocol and/or report format;

FIG. 16 is a graphical representation of an example UI for creating a new analysis protocol and/or report format;

FIGS. 17A through 17D illustrate example reports generated in response to invocation of one or more analysis protocol(s);

FIG. 18 is a flow chart of an example method for user-defined re-rating of billing information, in accordance with one aspect of the present invention;

FIG. 19 is a graphical representation of an example UI facilitating user re-rating of billing information;

FIG. 20 is a graphical representation of an example UI depicting an innovative paging structure, according to one aspect of the present invention; and

FIG. 21 is a storage medium having stored thereon a plurality of executable instructions to implement the financial service center, according to an alternate embodiment of the present invention.

DETAILED DESCRIPTION

This invention concerns an electronic financial management and analysis system and related methods and as such, represents an innovative extension of prior art EBPP systems. In this regard, the present invention overcomes a number of the limitations commonly associated with the prior art, some of which discussed above. For ease of illustration and explanation, and not limitation, the teachings of the present invention will be developed within the implementation context of a telephone services provider. Thus, the billing information presented in the illustrated examples will pertain to a telephone service provider implementation. It is to be appreciated, however, that the scope of the present invention extends well beyond the particular implementation described. Indeed, in describing the present invention, example network architectures and associated methods will be described with reference to the above drawings. It is noted, however, that modification to the architecture and methods described herein may well be made without deviating from spirit and scope of the present invention. Indeed, such alternate embodiments are anticipated.

Example System Architecture

Example Data Network

FIG. 1 illustrates a block diagram of a data network 100 including a server 108 providing financial management and analysis services. More specifically, in accordance with the teachings of the present invention, server 108 includes an electronic bill presentment, analysis and payment (EBPAP) agent 110 to facilitate the management and analysis of financial information from any of a number of billers. It will be appreciated, based on the description to follow, that server 108 including EBPAP agent 110 may well be provided by one or more biller(s), an independent application service provider (ASP), a financial institution, and the like.

As shown, network 100 is comprised of a number of network participants including user(s) 102 a . . . n, biller(s) 104 a . . . n, and financial institutions 106 a . . . n, each communicatively coupled to one another and server 108 via one or more networks 112 and/or 114, respectively. In addition, network 100 includes a number of data stores including, for example, a local data store 116 within server 108, and a network data store 118. As used herein, user(s) 102 a . . . n are the recipients of electronic billing information via the EBPAP agent 110, while biller(s) 104 generate billing information. Financial institutions 106 maintain asset backed accounts which may be used to facilitate financial transactions between the EBPAP provider(s), billers and users. It is to be appreciated, however, that use of financial institution asset backed accounts are not the only way to facilitate financial transactions via the EBPAP agent 110, as other types of accounts may well be used (e.g., such as credit backed accounts). It is to be appreciated that, as used herein, the label (e.g., user, biller, financial institution) given to a particular network participant at any point in time merely reflects the capacity in which the participant is accessing and utilizing the resources of EBPAP center 110 and is, in this regard, a dynamic descriptor. That is, at one point a participant may well access the EBPAP center 110 as a user 102 a . . . n, while at another moment the same participant is a biller 104 a . . . n (e.g., as in the re-rating operations scenario described below). Similarly, financial institutions 106 a . . . n may, at discrete points, alternatively be a user or a biller.

Moreover, it should be appreciated that each of the network participants accesses and utilizes the resources of network 100 through a computing platform. Accordingly, for purposes of this discussion, use of the term “business”, “biller”, “financial institution”, “user” or “network user” are each intended to represent the respective entity as well as their computing interface. As used herein the computing devices used by participants to access EBPAP center 110 of server 108 are intended to represent a broad range of computing devices known in the art. Indeed, according to an exemplary embodiment, any of a number of alternative computing and/or communications devices may well be used to access EBPAP center 110, as no special features or capability is required. Rather, EBPAP center 110 of server 114 selects an appropriate user interface suitable for the accessing computing device. Accordingly, computing devices such as, but are not limited to, personal computers, electronic kiosks, personal digital assistants (PDAs), wireless telephones, wireline telephones, thin-client terminals, and the like may well be used to access and utilize the resources of server 108.

As shown, networks 112 and 114 are intended to represent a wide variety of networks and a wide variety of communication technologies. In this regard, networks 112 and 114 may well include, but are not limited to, public data networks (Internet), the Automated Clearing House (ACH) network, communication networks (public switched telephony network (PSTN), cellular telephony network, and the like), private networks (enterprise wide area networks (WAN), data networks, and the like). Similarly, data stores 116 and 118 are each intended to represent any of a number of alternative storage media/devices known in the art. According to one example implementation, one or more local (116) or remote (118) data stores are used to store billing information generated by billers for presentment, analysis and/or payment by network participants registered to use EBPAP agent 110. Example data structures storing billing information will be described more fully below, with reference to FIGS. 4 and 5.

But for inclusion of the innovative EBPAP agent 110, server 108 is intended to represent any of a number of alternative computing devices communicatively accessible by network participants to utilize the services of EBPAP agent 110. As will be developed more fully below, EBPAP agent 110 provides network participants with a new level of billing information management, analysis and reporting features heretofore unavailable in the electronic bill presentment and payment (EBPP) field. More specifically, the innovative analysis and reporting engine, to be described more fully below, enable a user to modify billing information fields created by the biller; create new analysis protocols using user-defined fields of billing information; modify or remove existing analysis protocols, provided by the EBPAP agent 110 for all registered users, from a user's analysis profile; and/or create, modify or remove reporting formats from a user's report profile. Moreover, certain aspects of the invention, to be described more fully below, innovatively support the scalability of the EBPAP agent 110. Features such as, for example, the automated secure generation and reissuance of forgotten passwords, the ability to re-rate billers billing information, and an improved paging structure user interface. In this regard, the EBPAP agent 110 provides registered users with a powerful tool to uniquely manage and analyze financial information received from any of a number of billers. It will be appreciated, from the discussion to follow, that the innovative aspects of the EBPAP agent 110 may well be embodied in hardware, e.g., analog or digital circuitry, or in software executed by one or more processor(s) of the computer system(s).

Example Server Architecture

FIG. 2 illustrates a block diagram of an example computing system suitable for use as server 108, hosting the EBPAP agent 110 of the present invention. As introduced above, server 108 is intended to represent any of a plurality of computing devices known in the art. As depicted in the illustrated example embodiment of FIG. 2, server 108 includes one or more processing units 202, non-volatile memory 204, and a storage device 206 including executable instructions which, when executed by one or more processors 202, implement the EBPAP agent 110 of the present invention. Server system 108 also includes one or more input/output (I/O) ports 210 and a volatile system memory 212. In addition, certain implementations of server 108 include one or more input devices 208 and a display device 209, coupled as shown. It is to be appreciated that although the EBPAP center 110 is implemented as a software program, server 108 may alternatively support a hardware implementation as well. In this regard, but for the description of EBPAP agent 110, the following description of server 108 is intended to be merely illustrative, as computer systems of greater or lesser capability may well be substituted without deviating from the spirit and scope of the present invention.

As used herein, processing unit(s) of server 108 are programmed by means of executable instructions stored at different times in the various computer-readable storage media of the computer, e.g., volatile system memory 212, non-volatile memory 204, L1 or L2 cache memory of the processing unit(s) and the like. Application programs, operating systems, and other computing software are usually distributed on removable storage media such as, for example, floppy disks or CD-ROMs. From there, they are installed or loaded into the secondary memory of a computer, e.g., a mass storage device. At execution, they are loaded at least partially into the computer's primary electronic memory. Accordingly, it is to be appreciated that the invention described herein includes these and other various types of computer-readable storage media when such media contain instructions or programs for implementing the innovative steps described below in conjunction with a microprocessor or other data processor. The invention also includes the computer itself when programmed according to the methods and techniques described below. Furthermore, certain sub-components of the computer may be programmed to perform the functions and steps described below. The invention includes such sub-components when they are programmed as described. In addition, the invention described herein includes data structures, described below, as embodied on various types of memory media.

As used herein, but for the inclusion of EBPAP agent 110, processing unit(s) 202, non-volatile memory 204, storage device 206, input device 208, display 209, I/O ports 210 and volatile system memory 212 are each intended to be illustrative of such devices as they are well known in the art. Thus, they need not be described further.

Example EBPAP Agent

FIG. 3 illustrates a block diagram of an example electronic bill presentment, analysis and payment (EBPAP) center 110 incorporating the teachings of the present invention. In accordance with the illustrated example embodiment of FIG. 3, EBPAP center 110 includes one or more controller(s) 302, EBPP services 304, and an analysis and reporting engine 306, incorporating the teachings of the present invention. In addition, EBPAP center 110 advantageously includes management agent 308 and security agent 310, each comprising certain aspects of the present invention, to be described more fully below. EBPAP agent 110 is also depicted comprising an billing database interface 312 to access billing data store(s), a network interface 314, memory 316 including user account information 318 specifying analysis profiles 320 and report profiles 322, and one or more applications 324 including, for example, one or more user interface(s) 326, each coupled as shown. For ease of explanation and illustration, and not limitation, EBPAP agent 110 is depicted in FIG. 3 as a plurality of discrete functional blocks. It is to be appreciated, however, that one or more of the individual blocks may well be combined into a single block. Moreover, EBPAP agent 110 may well be implemented as a plurality of executable functions in software which, when executed, implement the services of financial transaction manager to be described.

As used herein, controller(s) 302 are intended to represent a wide variety of control and processing devices known in the art. Controller 302 manages the invocation of select EBPAP agents and services (304-310) upon receiving appropriate indications from higher-level resources such as, for example, user interface 326.

EBPP services 304 facilitate the electronic presentment of billing information to users 102 a . . . n from billers 104 a . . . n. In addition, EBPP services 304 enable users 102 to pay at least a portion of received bills utilizing credit and/or asset backed accounts via the well known credit and/or automated clearing house (ACH) financial transaction system. According to one aspect of the present invention, EBPP services 304 utilizes an innovative presentation method which enables a user to toggle between a detailed view of key information, or summary view. That is, EBPP services 304 enable, an authorized user to “expand” or “collapse” the presented bill to provide a user-defined amount of bill detail. Moreover, the ability to expand/collapse is provided on a line-item by line-item basis and may, in certain embodiment, also provide information describing the nature of the selected billing information. According to one embodiment, for example, expanding on a “tax” billing line item will provide a listing of all of the taxes associated with the received bill. Further selecting a tax line item will provide the user with a screen describing the nature of the tax and, perhaps, means by which the user can reduce or limit their tax liability.

In addition to the innovative expand/collapse feature, EBPP services function 304 also provides an innovative paging structure. Unlike the prior art, which simply provides “hyperlinks” to display the immediately surrounding ten (10) pages with “Next” and “Previous” links to view the next/previous ten pages, EBPP services 304 provides a paging hierarchy. According to one implementation, EBPP services 304 divides the pages of the bill into groups of ten (10) (e.g., 10, 20, 30, and so on) for bills under 200 pages, and groups of one hundred (100) for bills over 200 pages (e.g., 100, 200, 300, and so on). Once a particular range of pages is selected (e.g., 30), hyperlinks to 30-39 will be presented in addition to the hyperlinks to 10, 20, 40, 50 and so on. In this way, a user is generally only 2-3 “clicks” of the user I/O device (mouse) away from the billing page of interest. Thus, EBPP services 304 provide some innovative features which facilitate scaling of the EBPP solution for use by corporate customers.

Analysis and report generation engine 306 enables a user to effectively manage, analyze and create custom reports of billing information from one or more billers using the billing information hosted by the biller, financial institution, and/or third-party application service provider (ASP). As used herein, reports may well include textual information, graphical information, geographical distributions, and the like. According to one aspect of the present invention, to be developed more fully below, analysis and report generation engine 306 is selectively invoked by controller 302 to enable a user to establish an analysis and reporting profile comprising one or more analysis protocol(s) and/or one or more report format(s). In accordance with the teachings of the present invention, analysis and report generation engine 306 is used to create custom analysis protocols/report formats based, at least in part, on user-generated definitions and dependencies of the billing information. In addition, analysis and report generation engine 306 can be utilized to modify/remove analysis protocols/report formats from the analysis and report profile. In this regard, analysis and report generation engine 306 enables a user to analyze electronic information (e.g., billing information, call information, re-rating information, account information, and the like) at the source of such information and create custom reports, utilizing user-defined fields and dependencies established via management services 308.

As introduced above, management services 308 facilitates a number of account management functions including, for example, management of user profile information, management of payment and/or payment authorization information, and the customization of definitions and dependencies of billing account information facilitating user-defined analyses and/or report formats. Management services 308 enables a user to access the billing information and modify account information and dependencies, field definitions, analysis profiles and reporting formats. That is, the management services 308 enables authorized users to access and manipulate billing information at the server 108, i.e., without the prior art need of downloading the billing information to a local client computing device. Authorized users can establish billing information field dependencies within the billing information database for analysis and reporting purposes. In this regard, management services 308 fosters unprecedented access to and control over billing information at the source.

As used herein, each user account minimally includes at least one user identifier and associated password. According to an exemplary implementation, the user account also includes one or more references to personal information such as, for example, place of birth (e.g., one or more of city, state, province, country), month/day of birth, home zip code, postal address, mothers maiden name, email address, telephone number, facsimile number, and the like. According to one implementation, management agent 308 supports a hierarchy of users including, for example, master-users and basic-users. Such an implementation would be common, for example, with a corporate customer wherein the master-user would have full access and authority to review, analyze and generate reports for all billing information associated with one or more accounts of the corporate customer, to pay bills, etc. The basic-user has more limited access and authority privileges dictated by the master-user, to review and analyze the billing information or, perhaps, only a subset of the billing information associated with the corporate customer.

According to one aspect of the present invention, management services 308, enables a user to create and manage sub-accounts, to establish user profiles with different access rights to each of the different sub-accounts, and to manage payment authorization information. Implementation of the user hierarchy and the ability to create sub-accounts by management agent 308 facilitates the scalable financial management and analysis tool required to support larger corporate customers.

Security agent 310 provides the security features of the EBPAP center 110. It will be appreciated that communicating personal and financial information over potentially public data networks requires that steps be taken to preserve the confidential nature of such information. According to one innovative aspect of the present invention, to be developed more fully below, security agent 310 enables a user to decide (reflected in the user profile, for example) the level of security taken to preserve different sets of information. One user may decide, for example, that the transmission of billing information can occur over an unsecure communication link, whereas financial account information and/or personal information should minimally be encrypted and preferably be transmitted via a secure socket layer (SSL) connection from the user to the EBPAP center 110. In this regard, security agent 310 may well include support for any of a number of alternative encryption schemes including, for example, public key/private key encryption, message certification techniques, and the like.

In addition to managing the security of the communication channel, security agent 310 is responsible for authenticating accessing users. According to one example implementation, security agent 310 verifies received user identifier (e.g., a login identity) and password information against account information 318 residing in memory 316. If the accessing user is authenticated, the user is provided access to billing information in accordance with the access privileges identified in the account information 318. If the accessing user is not authenticated, they are not provided access to EBPAP agent 110, and security agent 310 logs the unauthorized attempt to gain access. In one embodiment, if an inordinate number of unsuccessful attempts are made to access particular account information, security agent 310 may generate a flag for a system administrator, security officer, or the like to notify the registered user of the access. According to one implementation, security agent 310 automatically issues an email to the registered email address of the targeted user to notify them of the unauthorized attempts.

In addition to the foregoing security features, security agent 310 provides a secure, automated password “reissuance” feature for users that forget their passwords, in accordance with one aspect of the present invention. If a user forgets their password, security agent 310 presents them with one or more questions based, at least in part, on the information contained in their user profile. If the accessing user is a legitimate user (i.e., he/she did, indeed, merely forget the password and is not an imposter) and is able to provide the security agent 310 with accurate answers to the questions posed, security agent 310 automatically generates a new password for the user and sends the new password to an address/location predefined by an authorized user (i.e., may include a master-user) in the initial set-up of the account (e.g., an email address). In this way, were an imposter able to provide security agent 310 with a correct user-ID and personal information associated with an authorized user, the imposter is not simply provided the new password, as it is instead sent to a personal address/location of the authorized user. Thus, the imposter would also have to gain access to the predefined address/location to retrieve the new password. Thus, it will be appreciated that security agent 310 provides a secure, yet scalable solution to the problem of servicing forgotten passwords.

Billing database, interface 312 and network interface 314 each provide the necessary communications link to data stores (e.g., 116, 118) and the networks (112, 114) to support the features of EBPAP agent 110. According to one example implementation, EBPAP agent 110 accesses and retrieves billing information from one or more databases (e.g., a SQL database, an Oracle database, a FoxPro database, an Access database, a LotusNotes database, a Filemaker database, and the like) resident on one or more data stores (116, 118) to facilitate the analysis and reporting features of EBPAP agent 110. Network interface 314 facilitates any communication to/from coupled data and/or communication networks (112, 114).

With continued reference to FIG. 3, memory 316 is shown comprising user account information 318 including default and user-defined analysis profiles 320, as well as default and user-defined report profiles 322. As will be developed more fully below, analysis and report generation engine 306 enable authorized users to modify (i.e., customize) or remove default analysis profiles or reports, as well as create their own analysis profiles or report formats. The profiles created by a user utilizing the analysis and report generation engine 306 are maintained with the account information 318 in the profiles 320 and 322, respectively. An example data structure of user account information is provided with reference to FIG. 4.

Turning briefly to FIG. 4, an example data structure containing user account information is provided, in accordance with one embodiment of the present invention. In accordance with the example embodiment of FIG. 4, data structure 400 is shown comprising a number of fields including, for example, user_Identification field 402, password field 404, personal information field(s) 406, account name field(s) 408, account definition field(s) 410, account code field(s) 412, geographic definition field(s) 414, time definition field(s) 416, category definition field(s) 418 and call group definition field(s) 420. According to one aspect of the present invention, EBPAP agent 110 provides user access to the definition of the category fields 402-420, and what information is represented in those fields. In this regard, EBPAP agent 110 enables a user to define the information to be analyzed and presented to the user, as appropriate to the particular application (e.g., telephone billing (shown), stock room supply management, corporate expense account management, and the like). More specifically, as will be discussed more fully below, EBPAP agent 110 enables a user to select which field information is utilized and the analysis(es) (e.g., statistical analyses, time/date analyses, etc.) to be run in developing user defined analysis protocols and reports.

In addition to account information 318 and profiles 320, 322, memory 316 may also include billing information (not shown) for analysis and/or reporting purposes by the EBPAP agent 110. According to one implementation, EBPAP agent 110 retrieves select billing information from one or more databases via billing dB interface 312 and stores it locally in, for example, memory 316 for analysis and reporting purposes. In alternate implementations, the retrieved billing information may well be stored within analysis and report generation engine 306 or within a cache (not shown) of controller(s) 302.

In addition the exemplary functions of EBPAP agent 110 introduced above, EBPAP agent 110 may advantageously include one or more application program(s) 324 including, for example, one or more user interface(s) 326. It is to be appreciated that the user interface (UI) 326 provides a user a means of interacting with and controlling the features of EBPAP agent 110. As alluded to above, user interface 326 is intended to accommodate any of a number of different computing devices which may access and utilize the features of EBPAP agent 110. In this regard, UI 326 is intended to represent any of a number of audio and/or visual user interfaces commonly known in the art. In one embodiment, for example, user interface 326 is comprised of a plurality of executable instructions which are communicated to a computing device accessing the EBPAP agent 110 to render a web page on a display of the computing device. In an alternate embodiment, user interface 326 is comprised of a touch-tone response system, wherein a user of a telephony device may interact with and selectively control the features and services of EBPAP agent 110. Depending on the detected capability of the computing device used to access the system, and the nature of the interface network (112/114), user interface 326 may be transmitted in an encrypted form to protect the sensitive nature of a user's account information. In the web page embodiment, described above, the web page would typically be encrypted according to security agent 310 settings and sent to the accessing computing device.

Given the foregoing introduction, it is to be appreciated that EBPAP agent 110 overcomes the inherent technical, scalability and analysis limitations of prior art EBPP systems, thereby providing a powerful financial management and analysis enterprise solution for individual and corporate customer's alike.

Example Data Structures

As used herein, data stores 116 and 118 are each intended to represent any of a number of storage devices/media for storing data structures. For example, data store 116, 118 may well be comprised of one or more of a floppy disk within a floppy disk drive, a hard disk drive, a redundant array of independent drives (RAID) system, a compact disk (CD) inserted within an accessible CD player, a digital versatile disk (DVD) inserted within an accessible DVD player, a magnetic tape within a tape drive, and the like. Such storage devices/media are well known to those skilled in the art and, thus, need not be described further.

As introduced above, the EBPAP agent 110 accesses and retrieves select billing information from one or more data stores, e.g., data store 116, 118, for presentation, analysis, report generation and payment by authorized users. An example data structure of billing information is presented with reference to FIG. 5, below.

FIG. 5 graphically illustrates an example data structure populated with billing information, in accordance with an example embodiment of the present invention. As introduced above, billing data structure may well be located in one or more of data stores 116 and/or 118. Moreover, according to one exemplary implementation, data structure 500 may actually be distributed as a number of individually linked data structures across such data stores. That is, although depicted as a flat data structure, this is for ease of illustration and discussion, and not intended to limit the scope of the present invention.

In accordance with the illustrated example embodiment of FIG. 5, billing data structure 500 is comprised of a number of fields including, for example, account number field(s) 502, account code field(s) 504, billed information field(s) 506, cost information field(s) 508, date field(s) 510, destination number field(s) 512, call duration (length) field(s) 514, rate information field(s) 516, call type field(s) 518 and time information field 520. According to one implementation, EBPAP agent 110 enables users to (re)define the fields in the billing data structure 500 to suit a particular application (e.g., telephone billing (shown), stock room supplies, corporate account management, etc.). In this regard, EBPAP agent 110 provides unprecedented access and management of information retained at billing information server 108.

As introduced above, in accordance with one example embodiment, data structure 500 is at least a subset of an example database comprising billing information. In accordance with the teachings of the present invention, controller 302, via dB interface 312, issues commands to retrieve information from and save information to the source of billing information. It is to be appreciated, however, that alternative database systems may well be substituted for the database without deviating from the spirit and scope of the present invention.

Example Operation and Implementation

Having introduced the operating environment and functional elements of the innovative EBPAP agent 110 with reference to FIGS. 1-5, above, the operation of the system will now be developed more fully below with reference to FIGS. 6-21.

As alluded to above, the agent 110 utilizes a user identifier and password combination to identify and authenticate users of the system. Thus, when first accessing the EBPAP agent 110, a user must enter a valid user_ID and password before they may proceed to utilize the services of EBPAP agent 110. As will be developed in greater detail below, security agent 310 establishes a communication channel in accordance with a user-defined security level noted in the user's account information. Regardless of the default security level established upon registration, whenever a user is working with financial account information and/or personal information security agent 310 establishes a secure communication channel using the secure hypertext transfer protocol (HTTPS) via the secure socket layer (SSL). Thus, EBPAP agent 110 and security agent 310 ensure that the truly confidential information associated with a user is protected, even if the user does not request a secure communication channel.

EBPAP Agent Invocation and Control

FIG. 6 illustrates a flow chart of an example method for invoking and controlling the financial management and analysis services of EBPAP agent 110, in accordance with one example embodiment of the present invention. As shown, the method begins with block 602 wherein server 108 receives a request from a user to access EBPAP agent 110. In response, server 108 passes the request to controller 302, which selectively invokes security agent 310 to authenticate the user_ID and password received in the access request, block 604. If the security agent 310 is unable to authenticate the requesting user in block 604, the process proceeds to the security agent 310 services denoted in FIG. 12 (discussed in greater detail below).

If, in block 604, security agent 310 is able to authenticate the user_ID and password, controller 302 selectively invokes an instance of user interface 324 for presentation to the requesting user. An example of a suitable graphical user interface is presented with reference to FIG. 7, below.

Briefly, FIG. 7 depicts an example illustration of a graphical user interface (UI) 700 suitable for use in accordance with the present invention. In this example implementation, the UI 700 is written in a “markup language”, such as HTML (Hypertext Markup Language), application server pages (ASP), extensible markup language (XML), and the like. It is to be appreciated, however, that the scope of the present invention is not limited to particular coding embodiments and, as such, alternative languages may well be used in implementing the teachings of the present invention. The UI 700 is rendered by an Internet browser application, such as the Internet Explorer browser from Microsoft Corporation, which executing on the accessing users computing/communication device.

In accordance with the illustrated example embodiment of FIG. 7, a web page comprising a banner (or, header) field 702, a menu (or, navigation) bar 704 and a message field 706 is provided. The banner field 702 will typically provide the name of the EBPAP service provider, or biller. In addition, controller 302 may further customize the banner field 702 with user-specific information such as, for example, advertisements, birthday greetings, special offers, coupons, and the like.

The menu/navigation bar 704 is shown comprising hyperlinks to a number of EBPAP features. More specifically, user selection of one or more of the buttons on the menu bar selectively invokes an associated feature of EBPAP agent 302. According to one implementation, for example, selection of the statement 710, summary 712 or detail 714 buttons selectively invokes one or more aspects of the EBPP service 304. In certain embodiments, selection of statement, summary or detail buttons (710-714) automatically invoke an instance of analysis engine to dynamically retrieve, analyze and present the requested information in a user-defined format. Thus, it is to be appreciated that analysis engine may well be invoked directly by a user, i.e., to execute a particular analysis, or by another element of EBPAP agent to fulfill another request. Selection of the graph button 716 enables a user to define and/or generate a report or graph. Selection of the settings button 718 invokes another page from which the user can modify account settings (i.e., selectively invoking management services 308) or analysis and report profile settings (i.e., selectively invoking analysis and report generation engine 306). Selection of the help button 720 selectively invokes an interactive assistant that provides answers to questions regarding one or more of billing information, using the analysis and reporting engine (306), security questions, registration and account questions, and the like. According to one embodiment, controller 302 receives the query and invokes a help application 324 (not specifically denoted) to handle users requests. The feedback button 722 selectively invokes an email service that enables the user to enter a question, comment or query and send it automatically to one or more of a biller, a financial institution, or the EBPAP provider.

In the message field 706, information associated with the management and analysis of one or more accounts (e.g., financial accounts, stock accounts, supply accounts, etc.) is provided. The actual information displayed in the message field 706 depends, at least in part, on the location of the user within the web-site (as denoted on the menu bar 704). As will be detailed below, when the user is in the statement, summary or detail UI, billing information of a certain detail will be presented for the user in message field 706. Alternatively, if the user is in the settings menu of the site, control fields will be presented in the message field enabling the user to further define billing information database fields, link billing fields, define analysis profiles, define report profiles, and/or perform certain administrative tasks (e.g., user profile information). It is to be appreciated that the layout of FIG. 7 is merely intended to be illustrative of one example implementation. Alternative UI's may well be substituted for UI 700 without deviating from the spirit and scope of the present invention.

Returning to the process of FIG. 6, once the main UI 700 is presented to an accessing user in block 606, the user interacts with the UI to selectively invoke one or more features of EBPAP system 110, blocks 608-618. More specifically, as alluded to above, selection of buttons 710-714 selectively invokes an instance of EBPP services 304, while selection of settings button 718 provides a user with another UI wherein they can selectively invoke an instance of management services 308 or analysis and report generation engine 306. It is to be appreciated, however, that analysis and reporting engine 306 may also be selectively invoked from within one or more of EBPP services 304 and/or management service 308, as discussed above. The ability to select various functions/services from the main menu 700 is illustrated in the flow chart as decision blocks 608, 614 and 616, respectively. If, for example, a user elects account administration (from the settings menu 718), security agent 310 determines whether a secure communication channel is established, block 610. If not, security agent 310 automatically establishes a connection at an appropriate security level, block 612. According to one implementation, when EBPAP is dealing with personal information (e.g., in the registration process), or with financial account information (e.g., the payment authorization process), security agent 310 establishes a secure communication channel utilizing HTTPs over SSL (as described above). The process of account administration then continues, with a secure connection, in FIG. 8.

In block 614, if the user elects to modify the analysis and/or reporting profiles, the process continues with reference to FIG. 14.

In block 616, if the user elects to utilize the EBPP services of EBPAP agent 110 (i.e., by selecting one of statement 710, summary 712, or detail 714 buttons), controller 302 selectively invokes an instance of EBPP services 304. More specifically, EBPP services 304 generates one or more database queries to access information associated with the requesting user from one or more data stores (116, 118) for presentation to the requesting user, block 618. As described above, EBPP services 304 enables a user to dynamically control the amount of information provided in the bill presentment, and will also enable the user to settle the account. Account settlement is performed through one or more of the ACH or a credit card clearing house.

It is to be appreciated that at any point in the process (or any page in the web-site), a user may return to the main UI 700 by pressing the home button 708. Indeed, a user may jump to the EBPP services UI by depressing buttons 710-714, the administration UI by pressing settings button 718 from any point in the process (or any page in the web-site).

Registration and Account Administration

FIG. 8 illustrates a flow chart of an example method for accessing and selectively invoking the resources of management services 308. As introduced above, management services 308 enables a user to manage payment authorization settings, user profile information and billing information account definitions and dependencies, in accordance with the teachings of the present invention. As above, management of these services is via a user interface. An example of a suitable user interface is provided with reference to FIG. 9.

FIG. 9 graphically illustrates an example management services UI, according to one example implementation of the present invention. As shown, management UI 900 includes hyperlinks which, when selected, enable a user to establish/modify payment authorization settings 902, user profile information 904, and one or more definitions and/or dependencies of the billing information 906 a . . . n, each of which will be described in greater detail below. In response to user interaction with UI 900 (i.e., selection of one or more hyperlink 902-906 a . . . n), management services 308 generates another UI in which the user can make the desired modifications.

Having introduced an example UI 900 for reference, the method of FIG. 8 begins with block 802 wherein controller 302 receives an indication to invoke management services 308. According to one example embodiment, the indication is generated in response to user selection of settings button 716 from the main UI 700. In response, management services 308 generates a UI (900) to provide the user with an interface to create, modify and/or remove elements from user account information 318, block 804. More specifically, as presented above, UI 900 enables the user to manage payment authorization information (902), user profile information (904) and/or customized account settings (906 a . . . n).

If, in block 806, an indication is received to modify payment authorization information, management services 308 provides the user with the current and/or payment authorization settings in user-manipulable fields, block 808. Providing the current and/or default settings in user-manipulable fields enables the user to modify select elements of the payment authorization process.

In block 810, management services 308 determines whether modification to the current and/or default payment authorization information has been made and, if so, updates the user account information to reflect the new information, block 812.

If in block 814, an indication is received to modify the user profile information, management services 308 provides the user with the current user profile information in user-manipulable fields, block 816. In addition to the foregoing method of invocation, controller 302 may well selectively invoke the user profile modification process upon the initial access of a heretofore unregistered user for the purpose of account registration. Presentation of the current user-profile information in user-manipulable fields enables a user to update select ones of the user profile information. The process continues with block 810, wherein management services 308 determines whether user modification to the user profile information has been received and, if so, updates the user account information to reflect the new information, block 812. An example UI facilitating modification to user profile information is provided with reference to FIG. 10.

FIG. 10 graphically represents an example UI 1000 wherein a user can provide/update user profile information. As shown, the UI 1000 includes one or more user-manipulable fields 1002 in which the user(s) 102 can provide requested user-profile information. According to one implementation, the requested user-profile information is defined by EBPAP agent 110. In an alternate embodiment, the user-profile information requested is established by one or more billers (104 a . . . n) which utilize the resources of EBPAP agent 110 as a service to their customers (e.g., one or more users 102 a . . . n). As shown, the provides the information requested in fields 1002 and selects the “ok” button 1004, when finished. In accordance with one implementation, failure to provide all of the requested information results in an error message, requesting that each of the fields be completed.

If, in block 818 of FIG. 8, management services 308 receives an indication to modify one or more of the customized account settings (906 a . . . n), management services 308 presents the user with a list of one or more customizable settings, block 820. In block 822, based on user selection of the one or more customizable settings, management services 308 presents the user with user-manipulable fields to define or modify current definition of the selected one or more settings. The process continues with block 810 wherein management services determines whether any user modifications have been made and, if so, updates the user account information to reflect the modifications, block 812. An example of UI's facilitating such customization is provided with reference to FIGS. 11A-D.

Recall from FIG. 9, management services 308 facilitates user-definition of a number of billing information elements and dependencies (e.g., 906 a . . . n). FIG. 11A illustrates an example UI 1100 facilitating user modification/removal of billing accounts, in accordance with one aspect of the present invention. As shown, UI 1100 displays accounts 1102 for which the user is authorized, along with user-modifiable descriptions of the accounts and dependency categories. UI 1100 enables an authorized user(s) 102 to change 1104 description(s) and/or category dependency definitions, or remove 1106 from the list. In accordance with one example implementation, presented in FIG. 11B, the user-manipulable fields may well contain pull-down menus of pre-populated options 1108. According to one exemplary embodiment, the pull-down menu 1108 is populated with user-defined information (i.e., dependency categories). Modification to description and category dependency definitions enables a user to customize analysis protocol(s) and/or report format(s) to reveal the desired information in a presentable format. Indeed, EBPAP agent 110 enables a user to particularly define analysis parameters (e.g., statistical (mean, max, min, variation), geographic distribution, account distribution, department distribution, etc.) and information parameters in defining an analysis protocol—a level of user control heretofore unavailable in the prior art.

FIG. 11C illustrates an example UI facilitating creation, modification and/or removal of account codes, according to one aspect of the present invention. As shown, UI 1120 illustrates a number of account codes 1122, with corresponding description definition fields and a category dependency definition field. A menu bar is provided wherein a user may elect to create 1124 a new account code, suggest 1126 account code settings, modify 1128 definition of an existing account code, and/or remove 1130 account codes from the list of available codes.

FIG. 11D illustrates an example UI 1130 facilitating user-defined categories, in accordance with one aspect of the present invention. As shown, UI 1130 includes a number of user-manipulable fields 1132 wherein a user may provide a description for a new account category. In accordance with the illustrated embodiments, account information is categorized by office location (e.g., Redmond, Seattle, Bellevue, etc.) and UI 1130 enables user-defined modification to the category listing, as well as creation of additional category types, e.g., job classification; department name, employee name, project identifier; job identifier, cost center identifier, and the like. In this regard, EBPAP 110 in general, and management services 308 in particular, facilitate unprecedented control over billing information, providing for the user-defined analysis and reporting of the present invention.

Automated, Secure Password Generation and Reissuance

FIG. 12 illustrates a flow chart of an example method for automatically generating and securely reissuing a password, in accordance with one aspect of the present invention. As shown, the method begins with block 1202 wherein controller 302 receives an indication from UI 324 that a user is asserting they have forgotten their password. In block 1204, controller 302 selectively invokes an instance of security agent 310 to verify that the asserting user is, indeed, an authorized user and, if so, to securely reissue a new password to the user.

In block 1206, to verify the authenticity of the user, security agent 310 provides the user with a UI containing one or more fields requesting personal information. According to one implementation, the personal information requested corresponds to at least a subset of information collected from the authorized user during the initial registration process. An example of just such a UI is presented with reference to FIG. 13.

Turning briefly to FIG. 13, a graphical representation of a user interface (UI) 1300 querying the user requesting password reissuance is presented, according to one implementation of the present invention. In accordance with the illustrated example embodiment, UI 1300 provides one or more fields 1302 in which the user is requested to provide some personal information to enable security agent 310 to verify the identity of the user requesting password reissuance. Once the fields have been completed, the user selects button 1304 to continue with the process.

Returning to FIG. 12, once the requested information is provided, security agent 310 compares the information provided against the information contained in the user account, block 1208. In block 1210, security agent 310 determines whether the information provided is a match. If not, security agent 310 issues a message to the requesting user that the password generation has failed, indicating that the user must contact a biller, financial institution, and/or the EBPAP service provider to re-activate account access, as the accessing user is denied access to EBPAP agent 110, block 1212. According to one example implementation, security agent 310 logs the fact that a failed attempt at password reissuance has occurred with the particular account. After a certain number of failed attempts have been exceeded, security agent 310 may block any future access to the particular account, instead requesting the user to contact customer service of the biller, financial institution, or EBPAP service provider for a new account/password.

If, however, in block 1210 security agent 310 receives accurate information from the user, security agent 310 automatically generates a new password for the user, block 1214. According to one implementation, security agent 310 generates a random combination of numbers and letters of a pre-defined length and assigns the new password to the authorized user in the user account, block 1216. In block 1218, security agent 310 generates a message for delivery to the user at a predefined address/location. According to an exemplary implementation, security agent 310 generates an email message including the new password and sends the message to an email address identified in the user account. It will be appreciated that alternate forms of communication may well be substituted, however, without deviating from the spirit and scope of this aspect of the present invention.

Analysis and Reporting Services

FIG. 14 illustrates a flow chart of an example method for customizing an analysis and report profile utilizing the resources of analysis and report generation engine 306, according to one example embodiment of the present invention. As shown, the method begins with block 1402 where, in response to a received indication, controller 302 invokes an instance of analysis and reporting engine 306. In accordance with the illustrated example embodiment, the indication is generated in response to user interaction with a UI. As introduced above, elemental features of the EBPAP agent 110 may be selectively invoked from any of the plurality of UI's described herein.

In block 1404, analysis and report generation engine 306 provides the requesting user with a UI, from which the user can elect to create, modify or remove an analysis/report. In block 1406, a list of available analyses/reports comprising the user's analysis and report profile is presented to the user within the UI. An example of a suitable UI facilitating management of the analysis and report profile is presented with reference to FIG. 15.

FIG. 15 illustrates an example UI facilitating management of the analysis and report profile using analysis and report generation engine 306, according to one example implementation of the invention. As shown, UI 1500 includes a pull-down listing 1502 of analysis and/or reports of the analysis and report profile, a number of user-manipulable fields 1504 reflecting analysis and/or report parameters and, in accordance with the illustrated example embodiment, what re-rating value is to be applied 1506. Using the UI 1500, a user can modify any of the identified parameters to tailor the named analysis/report to suit the individual needs of each user.

In block 1408, analysis and report generation engine 306 determines whether an indication to create a new analysis protocol and/or report format has been received. If so, analysis and report generation engine 306 provides the requesting user with a UI including current billing information categories and dependencies in a number of user-manipulable fields, wherein the user can modify any of the settings to design an analysis protocol and/or reporting format, block 1410. An example UI facilitating analysis protocol and/or report format design is presented with reference to FIG. 16.

FIG. 16 illustrates an example UI facilitating analysis protocol and/or report format design, in accordance with one example embodiment of the present invention. As shown, UI 1600 includes a field for naming the report (and/or analysis protocol) 1602, a plurality of user-manipulable fields comprising current billing information category definitions and/or dependencies 1604 from which the user can tailor a custom analysis protocol and/or report format, and a field for defining a re-rating value 1606 (if any).

In block 1412, analysis and report generation engine receives an indication from the user whether the appropriate billing account definitions and/or dependencies currently exist with which to design the custom analysis protocol and/or report format. If not, the process continues with block 818 of FIG. 8. If, however, the billing information definitions and dependencies are sufficient, analysis and report generation engine 306 creates a new analysis protocol and/or report format for inclusion in the analysis and report profile based, at least in part, on the user interaction with the design UI 1600, block 1414.

In block 1416, upon receiving the new analysis protocol/report format, analysis and report generation engine may well perform some verification diagnostics to ensure that the proposed protocol/format meets a minimum threshold of logic. According to one example implementation, for example, analysis and report generation engine 306 merely determines whether the proposed name of the protocol/report already exists; whether the proposed use of the definitions/dependencies is permissible; and the like.

In block 1418, analysis and report generation engine 306 updates the analysis and report profile to reflect the newly created protocol/report.

In block 1420, analysis and report generation engine 306 determines whether an indication to modify an existing analysis protocol/report format has been received. If so, analysis and report generation engine 306 provides the user with management UI 1500 and updates the analysis/report definitions in response to user selections of the user-manipulable fields (1502-1506), block 1422.

In block 1424, analysis and report generation engine 306 determines whether an indication to remove an existing analysis/report has been received from a user. If so, analysis and report generation engine 306 removes the analysis protocol and associated reports and updates the analysis and report profile of the user account information upon receipt of a confirmation from the user, block 1426. Alternatively, in block 1428, analysis protocols and report formats comprising the analysis and report profile will remain for selective invocation by the user.

FIGS. 17A through 17D illustrate example reports generated in accordance with the teachings of the present invention. According to one implementation, analysis and reporting engine 306 generates graphs and/or reports in accordance with user-defined settings and criteria upon invocation of the graph button 716, on UI 700. As shown, FIG. 17A depicts a bar chart 1702 of total call duration information broken down by the day of the week over a user defined period. It is important to note that the user, not the biller, financial institution or intermediary service provider define the report and/or graph formats. FIG. 17B depicts geographical distribution of call information 1704 directly on a map of the region of interest. FIG. 17C depicts a summary report 1706 of call information, including a summary line item for the accounting department, reference 1708. According to one implementation, the summary line item is implemented as an iconic selector (denoted by, for example, an underline, alternate textual color, etc.) if additional detailed information is available. If a user were to select the accounting line item 1708, a detailed information report of the accounting information is displayed, such as the one depicted in FIG. 17D. It is to be appreciated that, by enabling a user to define the report and/or graph formats at the source of the information, the user can eliminate the step of having to download (or worse, manually enter) the billing information for manipulation on the local computer. None of the static, proprietary prior art EBPP systems provide for user-defined report formatting and generation, much less user-defined analysis capability.

User Controlled Re-Rating of Billing Information

FIG. 18 illustrates a flow chart of an example method facilitating user definition of rating schedules and re-rating of billing information, in accordance with one aspect of the present invention. As introduced above, re-rating enables a primary user, i.e., a local provider of services (e.g., executive office suite) to re-rate (often, mark-up) the cost of services before presentation to a secondary user (or, end-user). EBPAP agent 110 facilitates the definition and re-rating of such services by the intermediary (i.e., primary user of the EBPAP, as opposed to a secondary, or end-user, which may or may not utilize the EBPP services of EBPAP). In accordance with the illustrated example embodiment of FIG. 18, the method begins upon receiving an indication that a user desires to re-rate billing information, block 1802. In response, controller 302 selectively invokes an instance of management services 308, which provides the authorized user with a UI enabling the user to create, modify or remove rate schedules from a listing of rate schedules which may be applied to select secondary user(s), block 1804. An example of a suitable UI is presented with reference to FIG. 19.

Turning briefly to FIG. 19, a graphical illustration of an example UI to create, modify or remove rate schedules from EBPAP agent 110 is provided, according to one example implementation. As shown, UI 1900 is comprised of a menu bar enabling a user to create new (1902) rate schedule(s), change existing rate schedule definitions (1904) or remove (1906) rate schedules from the list (1908) of available rate schedules. Selection of the new button 1902 from the menu bar causes management services 308 to invoke a UI enabling the primary user to define a new rate schedule. According to one implementation (not shown), the UI includes fields wherein the user can define one or more of the name of the rate schedule, a method of calculating the re-rating (i.e., a surcharge percentage to be added to base billing information, a fixed-fee surcharge to be added to base billing information, dynamically adjustable surcharge information based on time of call, length of call, call origin and/or call destination, the services used (e.g., analog services, digital services), bandwidth used, and the like), when the re-rating is to be applied (i.e., based on time of day, day of week, month, destination number, origin number, and the like), and to which secondary user(s) the re-rating schedule is to be applied. Similarly, selection of the change button 1904 enables a user to modify one or more of the above settings associated with the rate schedule. Selection of the remove button 1906 enables a user to remove one or more identified rate schedules from the rate schedule list 1908.

Returning to FIG. 18, the process continues by determining what function the primary user has selected from the rating UI 1900. If, in block 1806, the user has decided to create a new rating schedule, the user is provided with an interface including user-manipulable fields to facilitate naming of the new rate schedule, identification of the manner in which re-rating is to be applied, and, optionally, to which customers it will be applied. In block 1810, management services 308 receives the primary user's definitions for the new rate schedule and adds the rate schedule to the list of available rate schedules. In block 1812, management services 308 updates the user account information 316 with the rate schedule information, and applies the new rate schedules to existing and future billing information associated with the primary user.

If in block 1814, the user elects to change a rate schedule, management services 308 presents a UI to the user with the current definitions of the selected rate schedule, block 1816. In block 1818, in response to user modification of one or more parameters of the selected rate schedule, management services 308 updates the rate schedule definition in the user account information 316. The process continues with block 1812, wherein management services 308 applies the modified rate schedule to existing and future billing information associated with the primary user.

If, in block 1820, the user elects to remove a rate schedule from the list 1908 of rate schedules, management services 308 confirms that the user wants to permanently remove the rate schedule form the list, block 1822, before removing the rate schedule from the list. In block 1824, management services 308 updates the list of rate schedules to reflect deletion of the schedule, and the process continues with block 1812 wherein management services 308 updates select accounts to reflect the removed rate schedule.

Display Management

FIG. 20 graphically illustrates a detailed billing report 2000 incorporating an innovative paging feature/structure 2002 to enable a user to quickly locate a desired billing page, in accordance with one aspect of the present invention. As alluded to above, billing information may span tens to hundreds of pages, and an improved paging structure is needed to quickly traverse the pages to find a desired page. As shown with reference to FIG. 20, controller 302 identifies the total number of pages to be displayed, and divides the total into even subsets of, for example, 10 page increments. If a user is interested in page 25, for example, the user selects a hyperlink associated with pages 20-30, whereupon the hyperlink “20” is replaced by hyperlinks to individual pages 21-29, with the original hyperlinks 10, 30, 40, etc. still displayed. It will be appreciated that such a paging structure enables a user to quickly “jump” to a desired page in fewer steps than prior art paging methods.

Although depicted in accordance with the EBPAP system 110, it is to be appreciated that the paging structure of the present invention may well be applied to other systems such as, for example, a search engine, stand-alone applications (e.g., accounting and book-keeping applications), database systems, e-commerce retail sites, and the like. Such alternate implementations are anticipated within the scope and spirit of the present invention.

Alternate Embodiments

FIG. 21 is a block diagram of a storage medium having stored thereon a plurality of instructions including instructions to implement the teachings of the present invention, according to yet another embodiment of the present invention. In general, FIG. 21 illustrates a storage medium/device 2100 having stored thereon a plurality of executable instructions 2102 including at least a subset of which that, when executed, implement the EBPAP agent 110 of the present invention. When a executed by a processor of a host system, the executable instructions implementing EBPAP agent 110 facilitate account management and analysis for any of a plurality of financial accounts including, but not limited to, telephone accounts, credit card accounts, utility bills, mortgage accounts, brokerage accounts, and the like.

As used herein, storage medium 2100 is intended to represent any of a number of storage devices and/or storage media known to those skilled in the art such as, for example, volatile memory devices, non-volatile memory devices, magnetic storage media, optical storage media, and the like. Similarly, the executable instructions are intended to reflect any of a number of software languages known in the art such as, for example, C++, Visual Basic, Hypertext Markup Language (HTML), Java, eXtensible Markup Language (XML), and the like. Moreover, it is to be appreciated that the storage medium/device 2100 need not be co-located with any host system. That is, storage medium/device 2100 may well reside within a remote server communicatively coupled to and accessible by an executing system. Accordingly, the software implementation of FIG. 21 is to be regarded as illustrative, as alternate storage media and software embodiments are anticipated within the spirit and scope of the present invention.

Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as exemplary forms of implementing the claimed invention. 

1. A system, comprising: one or more network devices, each having stored thereon billing information from one or more billers; and one or more other network devices, wherein each of the other network devices is operable to access at least some of the billing information and is configured to perform actions, including: enabling a customer to define and modify customer-defined fields for a subset of the billing information, wherein the customer is different from the one or more billers; enabling the customer to create and modify customer-defined category dependencies for the subset of the billing information; creating a customer-defined analysis that utilizes the customer-defined fields and customer-defined category dependencies; generating a customer-defined report by performing the customer-defined analysis on the subset of the billing information; and providing the customer-defined report to the customer.
 2. The system of claim 1, wherein the customer-defined-analysis further includes one or more analysis protocols and one or more report formats.
 3. The system of claim 1, wherein the customer-defined analysis further includes one or more customer-defined rating schedules.
 4. The system of claim 3, wherein the one or more other network devices is further configured to perform actions, including: re-rating a cost of services for the subset of the billing information based on the customer-defined rating schedules.
 5. The system of claim 1, wherein the one or more other network devices is further configured to perform actions, including: re-rating a cost of services for the subset of the billing information by adding to base billing information at least one of a surcharge percentage, a fixed-fee surcharge, or a dynamically adjustable surcharge.
 6. The system of claim 1, wherein the customer is a master-customer in a hierarchy of customers that includes at least master-customers and basic-customers.
 7. The system of claim 1, wherein the customer-defined report includes at least one of textual information, graphical information, or geographical distribution information.
 8. A network device, comprising: a transceiver for communicating with at least one customer device over a network; a data store for storing billing information from one or more billers; and a processor for enabling actions, the actions comprising: receiving, from a customer of a customer device of the at least one customer device, customer-defined fields and customer-defined category dependencies for at least a subset of the billing information, wherein the customer is different from the one or more billers; generating a customer-defined report by performing a customer-defined analysis on the subset of the billing information, wherein the customer-defined analysis utilizes the customer-defined fields and the customer-defined category dependencies; and providing the customer-defined report to the customer.
 9. The network device of claim 8, wherein the processor further enables actions, the actions comprising: enabling the customer to select which customer-defined fields are utilized in the customer-defined analysis.
 10. The network device of claim 8, wherein the customer-defined fields include billing information fields created by the one or more billers and modified by the customer.
 11. The network device of claim 8, wherein the processor further enables actions, the actions comprising: enabling the customer to create custom analysis protocols using the customer-defined fields.
 12. The network device of claim 8, wherein the processor further enables actions, the actions comprising: enabling the customer to create custom analysis protocols using the customer-defined category dependencies.
 13. A computing system, comprising: a billing data store, to store billing information from one or more billers; an analysis engine, coupled to the billing data store, to generate a user-defined report by performing a user-defined analysis on at least a subset of the billing information, wherein the user-defined analysis utilizes at least user-defined definition fields and user-defined category dependencies; and a user interface, coupled to the analysis engine, to enable a user to interact with and control the analysis engine, wherein the user defines the user-defined definition fields and the user-defined category dependencies using the user interface, wherein the user is different from the one or more billers.
 14. The computing system of claim 13, wherein the user interface enables the user to select which user-defined definition fields are utilized in the user-defined analysis.
 15. The computing system of claim 13, wherein the user interface enables the user to modify the user-defined definition fields.
 16. The computing system of claim 13, wherein the user interface enables the user to modify the user-defined category dependencies.
 17. The computing system of claim 13, wherein the user interface enables the user to modify existing analysis protocols.
 18. The computing system of claim 13, wherein the user interface enables the user to modify billing information fields created by the one or more billers.
 19. The computing system of claim 13, wherein the user interface enables the user to create custom analysis protocols using the user-defined definition fields and the user-defined category dependencies.
 20. The computing system of claim 13, wherein the user interface enables the user to re-rate the subset of the billing information. 